Recorded Future - Log Ingestion

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index


Attribute Value
Connector ID RecordedFuture
Publisher Recorded Future
Used in Solutions Recorded Future
Collection Method CCF
Connector Definition Files RecordedFuture_ConnectorDefinition.json
Microsoft Learn View on Learn

Imports Recorded Future data into Microsoft Sentinel via the Log Ingestion API. Writes playbook alerts to RecordedFuturePlaybookAlerts_V2_CL, classic alerts to RecordedFutureClassicAlerts_V2_CL, threat map data to RecordedFutureThreatMap_V2_CL and RecordedFutureThreatMapMalware_V2_CL, and sandbox results to RecordedFutureSandboxResults_V2_CL.

Tables Ingested

This connector ingests data into the following tables:

Table Transformations Ingestion API Lake-Only
RecordedFutureClassicAlerts_V2_CL ✓ ✓ ✓
RecordedFuturePlaybookAlerts_V2_CL ✓ ✓ ✓
RecordedFutureSandboxResults_V2_CL ✓ ✓ ✓
RecordedFutureThreatMapMalware_V2_CL ✓ ✓ ✓
RecordedFutureThreatMap_V2_CL ✓ ✓ ✓

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

1. Step 1 — Deploy Data Connectors infrastructure

Deploys the shared Data Collection Endpoint (DCE), Data Collection Rules (DCRs), Log Analytics tables, and this connector definition tile. Deploy this into the same resource group as your Log Analytics Workspace.

Deploy to Azure

2. Step 2 — Deploy the Recorded Future Custom Connector

The custom connector handles authentication towards the Recorded Future API. Deploy it once — it is shared by the playbooks.

Deploy to Azure

3. Step 3 — Deploy playbooks

Deploy one or more playbooks depending on your use case. No manual configuration is needed — each playbook connects to the Data Connectors infrastructure deployed in Step 1 automatically.

Additional Documentation

📄 Source: [Recorded Future\Data Connectors\README.md](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Recorded Future\Data Connectors\README.md)

Data Connectors

Files

RecordedFuture_ConnectorDefinition.json

Customizable connector definition for the Recorded Future - Log Ingestion tile. Listed in ../Data/Solution_RecordedFuture.json and baked into ../Package/mainTemplate.json by the packaging tool. This is what makes the connector appear in the Sentinel Data Connectors gallery after a Content Hub / solution install.

azuredeploy.json

Standalone ARM template that deploys the full infrastructure stack shared by the Log Ingestion API playbooks:

Used by the "Deploy to Azure" button in the Playbooks README and in the connector's own instruction steps. Deploy this before deploying any of the 6 playbooks that use the Log Ingestion API (RecordedFuture-Alert-Importer, RecordedFuture-Playbook-Alert-Importer, RecordedFuture-ThreatMap-Importer, RecordedFuture-ThreatMapMalware-Importer, RecordedFuture-Sandbox_StorageAccount, RecordedFuture-Sandbox_Outlook_Attachment).

Known duplication

Connector tile

The connector UI tile content exists in two forms due to limitations of the packaging/deployment model:

Content Packager source Standalone ARM
Connector UI tile RecordedFuture_ConnectorDefinition.json azuredeploy.json (Microsoft.OperationalInsights/workspaces/providers/dataConnectorDefinitions resource, kind: Customizable)

If you update one (queries, description, instruction steps, connectivity criteria, etc.), update its counterpart.

Upgrading

azuredeploy.json has no automatic Content Hub "update available" notification — it's a standalone template, not a tracked content item. When it changes (e.g. new DCR/table columns), existing customers must manually redeploy it (same resource group) to pick up the change. Check metadata.releaseNotes here and the top-level ReleaseNotes.md for what changed.


Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index